The Meridian360 Portal integration setup files include numerous custom functions that must be imported into the vault configuration. These are defined in the files that you installed as described in Installing the files.
To add the custom functions:
Following are some remarks about Meridian360 Portal script for vaults based on the BlueCielo Industry Template. If necessary, modify the script to meet your business requirements.
When a document is imported from Meridian360 Portal and if content was modified, it is routed to the Review state. If the document was not modified, it is routed to Under Change.
For documents that are returned in review packages, the property AMDocumentPropertySet._HAS_RENDITION_REDLINES is set to TRUE indicate on the Document page the presence of any annotations. For this feature to work requires that you merge the registry file Configuration\SafeProperties.reg by running it.
Sends a notification message upon package import. Make sure the notification is configured in your environment as described in Configuring event notifications or remove the following line:
Vault.SendNotification "PackageImported", Package
When a released document is added to a package, a workflow is started.
This function might need to be adjusted to find the document upon import from the returned package.
This event writes the transmittal header. See details in About the transmittal template.
These functions are used to find and validate the packages in a project. They use the workflow status text as criteria. If the default package workflow status text was modified, the following line should be adjusted accordingly.
sStatus = "Under Change"
This procedure is used to set properties for new packages. Review this code carefully.
See Configuring the project folder type.
This event is used to send a package to Meridian360 Portal and also to execute the relevant workflow transition on all documents included in the package. Review the code carefully and modify it to match your custom workflow.
This command is used to accept a conflicting document. While doing this, the document is moved to the relevant workflow state. Review the code carefully and modify it to match your custom workflow.